|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2046 (1996)
|
|
Title:
|
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track (Draft Standard)
|
|
3.
|
Justification for the specific reference:
|
|
|
This RFC is well-known as a method to identify the format of messages. Application event handling for IPTV services also uses this standard for identifying types of payload data.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=2046
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Draft Standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Draft Standard.". RFC 2046 was published in November 1996. RFC 2046 specifies Multipurpose Internet Mail Extensions, a draft Internet standard for the Internet community. It is published by the IETF at http://www.ietf.org/rfc/rfc2046.txt.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 2046 is a component of the basic suite of internet protocols and standards and is widely used by the internet community.Obsoletes: RFCs 1521, 1522, 1590. Updated by: RFC 2646, RFC 3798, RFC 5147, RFC 6657, RFC 8098. Errata exist.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
None.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
